missing separate debuginfos

GDB debugging start, error, the message is as follows:Detaching after fork from child process 4112.Program exited normally.Missing separate Debuginfos, Use:debuginfo-install cyrus-sasl-lib-2.1.23-15.el6_6.2.x86_64 glibc-2.12-1.149.el6_ 6.5.x86_64

When debugging with GDB under CentOS6.4,When using the BT (breaktrace) command, the following prompt pops up:First day Tip:Missing separate Debuginfos, Use:debuginfo-install glibc-2.12-1.107.el6.i686Problem is not resolved, the next day

When using GDB for debugging under CentOS6.4, When you use the BT (breaktrace) command, the following prompts are displayed: First day Tip: Missing separate Debuginfos, Use:debuginfo-install glibc-2.12-1.107.el6.i686 The problem is not resolved,

The following issues were encountered when debugging segmentation fault problems in GDB:Program received signal SIGABRT, aborted.0x00007ffff73eb925 in Raise (sig=6) at.. /nptl/sysdeps/unix/sysv/linux/raise.c:64Inline_syscall return (Tgkill, 3, PID,

When debugging with GDB on CentOS6.5, prompt missing separate debuginfos, Use:debuginfo-install glibc-2.12-1.132.el6.i686 First Modify/etc/ Yum.repos.d/centos-debuginfo.repo inside the Debuginfo directory enabled=1 then yum install

Using GDB on CENTOS7:$ gdb php$ run/home/www/2.phpAfter running run, follow a long hint:....Missing separate Debuginfos, Use:debuginfo-install cyrus-sasl-lib-2.1.26-17.el7.x86_64 glibc-2.17-55.el7_0.3.x86_64 keyutils-libs-1.5.8-3.el7.x86_64

Environment: centos6.2 64-bitOperation: Use GDB to debug the C ++ query MySQL database programCause:Solution:1. Modify the enabled parameter in the file/etc/yum. Repos. d/CentOS-Debuginfo.repo to 1, such as: VI/etc/yum. Repos.

# in Nginx and PHP-FPM next visit Nginx on the instant 502 question Php-fpmsignal 7 (Sigbus) Failure phenomenon Use the tinkphp3.2.x frame, the page occasionally appear a visit Nginx on the report 502 bad Gateway, not wait for a period of time

> For reprinting, please specify the Source: piao2010's blog, the drifting code. Thank you! Pai_^ > Link to this article: Why does the dynamic library (SO) of the process overwritten by CP cause coredump? The question behind the previous blog "Linux

First, start>>gdb startGDB debugs the debug symbols before debugging, that is, the compile time Add –g option, such as GCC file.c–g–o targetThere are 3 ways to enable GDB, one to start the core, and one to attach a running process.1. GDB 2. GDB